Skip to content

LLP 0290/0291: local inference is an out-of-tree lane; core owes a projector precedence contract - #956

Open
bgmcmullen wants to merge 1 commit into
masterfrom
llp/0290-local-inference-capture-lane
Open

LLP 0290/0291: local inference is an out-of-tree lane; core owes a projector precedence contract#956
bgmcmullen wants to merge 1 commit into
masterfrom
llp/0290-local-inference-capture-lane

Conversation

@bgmcmullen

Copy link
Copy Markdown
Contributor

What this is

The two local-inference LLP drafts from the 2026-08-18 working session, committed as-is on their own branch. Both are Status: Draft - this PR records them; nothing here is Accepted, so no agent work derives from it yet.

  • LLP 0290 (decision): capturing a local inference server (Ollama, LM Studio, llama.cpp, vLLM) is not bundled work - the hypaware.ai-gateway@2.0.0 capability names custom integrations as a consumer and the install path is complete, so the whole lane is buildable out of tree. What core owes is the one thing an out-of-tree author cannot secure for themselves: a documented projector dispatch precedence, because today such a plugin's correctness rests on outranking an undocumented priority number inside @hypaware/codex.
  • LLP 0291 (plan): three tasks that publish and pin that precedence band, shippable independently of anything using it. The local-inference plugin itself is explicitly out of scope per LLP 0290 #ownership.

Renumbering

The drafts were written as 0266/0267. Both numbers have since been claimed: 0266 by cli-compatibility-rollover on master, and open PRs claim through 0289, so the docs take 0290/0291. All internal cross-references (headers, Related: lines, @ref mentions, relative links and anchors) are updated to match; no content changes otherwise.

🤖 Generated with Claude Code

…ojector precedence contract

Two docs drafted 2026-08-18, renumbered from their draft numbers
0266/0267 (both since claimed on master and by open PRs):

- LLP 0290 (decision, Draft): capturing a local inference server
  (Ollama, LM Studio, llama.cpp, vLLM) is not bundled work; the
  hypaware.ai-gateway@2.0.0 capability and install path already support
  it out of tree. What core owes is the one thing a third-party adapter
  cannot secure for itself: a documented projector dispatch precedence,
  because today such a plugin's correctness rests on outranking an
  undocumented priority number inside @hypaware/codex.

- LLP 0291 (plan, Draft): the three tasks that publish and pin that
  precedence band. The local-inference plugin itself is explicitly out
  of scope.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant